I used Hyper-V in the past to run the Windows Phone emulator on my Win8.1 Pro-running computer, but I had disabled it (as in disabled the feature) because it conflicted with VMWare. Now I need to run the emulator again, but after re-enabling Hyper-V, every time I try to start a VM I get the infamous "something something cannot begin because the hypervisor is not running".

I've gone and looked through many forums posts and tried many things, but to no avail. Here's some stuff that I've tried:

• Completely uninstalling VMWare
• Disabling the Hyper-V feature and re-enabling it between cold boots
• Going into my BIOS and turning on and off virtualization between cold boots
• Making sure DEP is turned on (hardware-wise as well)
• bcdedit /set hypervisorlaunchtype auto
  

Here are some of the readouts given by programs that I've seen recommended for troubleshooting this problem:

> systeminfo.exe

Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

> CoreInfo.exe

Coreinfo v3.21 - Dump information on system CPU and memory topology
Copyright (C) 2008-2013 Mark Russinovich
Sysinternals - www.sysinternals.com

Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
HYPERVISOR      -       Hypervisor is present
VMX             *       Supports Intel hardware-assisted virtualization
EPT             *       Supports Intel extended page tables (SLAT)

> wmic OS Get DataExecutionPrevention_Available
DataExecutionPrevention_Available
TRUE

> wmic OS Get DataExecutionPrevention_Drivers
DataExecutionPrevention_Drivers
TRUE

> bcdedit /enum

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 8.1
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {945303b9-466f-11e3-9a3b-c5a07e9d086f}
integrityservices       Enable
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {1235a14d-466d-11e3-9a3b-c5a07e9d086f}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

Here are some images too, showing that my machine is SLAT capable as well as having hardware-enabled DEP: http://imgur.com/a/FTMmy

I've also gone through the event viewer, but I've seen nothing that grabs my attention.

Any ideas? This would bother me less if I hadn't been able to get this working in the past with zero problems whatsoever. And I know that between the time it had worked and now, I have not had any hardware changes, as well as any major driver updates.

Thanks.

• Edited by yet2bedefined Sunday, February 16, 2014 12:33 AM

Hi

Have you tested the dism command to get Hyper-V working

dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

I'm out of ideas. However I would start by uninstalling all Hyper-V features and reboot, twice.

In Event Viewer go to View and select Show Analytic and Debug Logs which will present even more logs. Make sure to Enable at least the Hyper-V-VMMS Analytic log.

Install all Hyper-V features, reboot twice.

If Hyper-V is still not operational, check the Event log for any clues and post them back here.

What machine (hardware make and model) are you running?

• Edited by yet2bedefined Monday, February 17, 2014 9:57 AM

Re-enabling Hyper V and the reboots didn't seem to change anything.

I enabled analytic logging for Hyper-V-VMMS and it spat out some nasty looking errors. Most of them are variations of one another, here are some of them:

Failed to open global VID statistics object! HRESULT = 0x80070103

TesthooksWrapper::Initialize: Load RdvTestHooks.dll failed. HRESULT=0x8007007e. All test hooks checks will return default values.

Synth3dPhysicalGPUManager::BecomeFunctional faced errors 0
[VmVirtualNetworkProvider::GetSwitchInfo (vmvirtualnetworkprovider.cpp:457)] IOCTL_SWITCH_GET_INFO for [228CC125-D7B6-4F18-932D-7B69012ADA1A] failed (0x80070002)

throw VmGeneralSystemException((DWORD) 2)

class Vml::VmGeneralSystemException caught in VmEthernetConnectionProvider::ReattachValidationPorts! HRESULT = 0x80070002

Failed to set remoting certificate for VM 041DA3C1-8DDB-4063-B9FB-D7D10C6E0155!

Failed to set allowed hash algorithms for VM A18AB27A-70D0-4811-9907-87A5D54E6168!

LpStatistics::Initialize: VidOpenStatisticsHandle failed! Error = 259

ServiceModule::PrepareToRunSelf: Failed to initialize LpStatistics with HRESULT: 80070103

Failed to register decoupled WMI provider VmmsWmiInstanceAndMethodProvider in namespace root\virtualization! HRESULT = 0x80041011

I'm running a laptop, a Lenovo Y580. Not exactly meant for development, but it gets the job done for me (and it has worked in the past, as I've mentioned above). Here's the basic specs, tell me if you need anything more:

Operating System
    Windows 8.1 Pro 64-bit
CPU
    Intel Core i7 3610QM @ 2.30GHz
    Ivy Bridge 22nm Technology
RAM
    8.00GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard
    LENOVO Product Name (U3E1)
Graphics
    Generic PnP Monitor (1920x1080@60Hz)
    Intel HD Graphics 4000 (Lenovo)
    2048MB NVIDIA GeForce GTX 660M (Lenovo)
Storage
    465GB Western Digital WDC WD5000BPKT-24PK4T0 (SATA)
Optical Drives
    MATSHITA BD-MLT UJ260
Audio
    Realtek High Definition Audio

Speccy lists the processor as supporting virtualization, as well as having it enabled.

Again, thanks for the help so far.

Hi

Did you try from an elevated command prompt

dism.exe /Online /Disable-Feature/featurename:Microsoft-Hyper-V /All

and

dism.exe /Online /Enable-Feature/featurename:Microsoft-Hyper-V /All

• Edited by yet2bedefined Monday, February 17, 2014 10:45 AM

Hi

Did you get any errors from running the commands?

Hi

Check that TrustedInstaller has FULL access on the Windows\WinSxS folder and subfolders

Hey. I didn't encounter any errors running the commands, they both executed completely and successfully.

TrustedInstaller indeed has full access to the Windows\WinSxS folder (and its subfolders).

Could you have disabled the Virtual hardware assist in the BIOS settings?

Check your BIOS and if Intel based make sure that you enable VT and Execute Disable. I do not remember the AMD equivalent.

Ed

Hi

Look in Device Manager are there any VMware device/network drivers?

In VIEW select Show Hidden Devices

Could you have disabled the Virtual hardware assist in the BIOS settings?

Check your BIOS and if Intel based make sure that you enable VT and Execute Disable. I do not remember the AMD equivalent.

Ed

VT and DEP are both enabled in my BIOS. I went and disabled and re-enabled them between cold boots to no effect.

Hey.

I've gone and looked through all of the categories and I can't find anything that seems to belong to VMware.

Just wanted to check in just in case someone else has this problem.

I sadly still don't know the exact cause, but I went and did a repair install of Windows 8.1, and now it miraculously works. Seeing as a repair install just rolls back all updates and drivers, I think it must have been a driver issue, although  I don't know what the conflicting driver was. I fear reinstalling VMWare though!

Thanks for the guidance everyone.

• Marked as answer by yet2bedefined Thursday, February 27, 2014 6:51 AM

Just wanted to check in just in case someone else has this problem.

I sadly still don't know the exact cause, but I went and did a repair install of Windows 8.1, and now it miraculously works. Seeing as a repair install just rolls back all updates and drivers, I think it must have been a driver issue, although  I don't know what the conflicting driver was. I fear reinstalling VMWare though!

Thanks for the guidance everyone.

I have been following this thread eagerly because I have the exact same problem.  The last time I started up my VMs in 8.1 Pro Hyper-V (Svr 2012 R2 and Kali Linux for my study) was just before Christmas and all was perfect then and they have been untouched since then.  Now, I try to start them for the new college year and "the hypervisor is not running."  I have tried everything suggested in the thread so far.

This is great because it points us in the direction of the cause of the problem (an update or driver), though I may yet do a repair install myself as I need these VMs to be running.

Did you ever figure this out?

I didn't figure mine out.  I had to do a clean installation of Windows because the repair install failed with the error message "We couldn't update the system reserved partition."  I started from scratch, this time in UEFI mode rather than legacy BIOS mode (I just took the opportunity because it's better) and starting with an 8.1 ISO rather than the plain 8 license I had before.  (I wonder if Hyper-V didn't like the upgrade from 8 to 8.1 in some way, but I can only wonder.)

All available Windows updates have been applied and it has the latest BIOS and drivers.  I should mention that I tested Hyper-V functionality after each stage of the software build (after BIOS update, each driver installation and major software installation - more innocuous programs were installed in blocks - I was thinking, surely some things can't affect Hyper-V).  OK at every stage starting just after installation of Windows and Hyper-V.

I have had no problems in Hyper-V since then.

• Edited by MartyvH Saturday, June 21, 2014 12:30 AM Clarified

I used Hyper-V in the past to run the Windows Phone emulator on my Win8.1 Pro-running computer, but I had disabled it (as in disabled the feature) because it conflicted with VMWare. Now I need to run the emulator again, but after re-enabling Hyper-V, every time I try to start a VM I get the infamous "something something cannot begin because the hypervisor is not running".

I've gone and looked through many forums posts and tried many things, but to no avail. Here's some stuff that I've tried:

• Completely uninstalling VMWare
• Disabling the Hyper-V feature and re-enabling it between cold boots
• Going into my BIOS and turning on and off virtualization between cold boots
• Making sure DEP is turned on (hardware-wise as well)
• bcdedit /set hypervisorlaunchtype auto
  

Here are some of the readouts given by programs that I've seen recommended for troubleshooting this problem:

> systeminfo.exe

Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

> CoreInfo.exe

Coreinfo v3.21 - Dump information on system CPU and memory topology
Copyright (C) 2008-2013 Mark Russinovich
Sysinternals - www.sysinternals.com

Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
HYPERVISOR      -       Hypervisor is present
VMX             *       Supports Intel hardware-assisted virtualization
EPT             *       Supports Intel extended page tables (SLAT)

> wmic OS Get DataExecutionPrevention_Available
DataExecutionPrevention_Available
TRUE

> wmic OS Get DataExecutionPrevention_Drivers
DataExecutionPrevention_Drivers
TRUE

> bcdedit /enum

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 8.1
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {945303b9-466f-11e3-9a3b-c5a07e9d086f}
integrityservices       Enable
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {1235a14d-466d-11e3-9a3b-c5a07e9d086f}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

Here are some images too, showing that my machine is SLAT capable as well as having hardware-enabled DEP: http://imgur.com/a/FTMmy

I've also gone through the event viewer, but I've seen nothing that grabs my attention.

Any ideas? This would bother me less if I hadn't been able to get this working in the past with zero problems whatsoever. And I know that between the time it had worked and now, I have not had any hardware changes, as well as any major driver updates.

Thanks.

your CPU has some limitations for visualization with the new HAL

http://ark.intel.com/products/64899/Intel-Core-i7-3610QM-Processor-6M-Cache-up-to-3_30-GHz

notebook mobile boxes were not generally designed for server roles, unlike desktops

newer processors will gain better support with Windows 8.1 professional which now included Hyper-V as a feature.

you will need to consult cpu manuals deeply to identify suitable models

I am not really intending on hijacking this thread, "but" I am seeing almost the same exact errors when I enable logging as MartyvH. My processor is

http://ark.intel.com/products/75133/Intel-Core-i7-4930MX-Processor-Extreme-Edition-8M-Cache-up-to-3_90-GH/

Computer Dell Precision M4800

32 Gigs Memory

The suckyness comes from the fact that Hyper-v Worked great before doing a clean install and upgrading my bios. I have added 2 touch screen dell monitors, but can't imagine that is the issue. I have since then went back to the older bios version, used different drivers, did a fresh build, did a repair, but nothing has solved my issue to this point. Should I be going to Dell or Microsoft for resolution?

thanks

• Edited by WhosTheBadCoderNow Friday, June 20, 2014 3:09 PM

your CPU has some limitations for visualization with the new HAL

http://ark.intel.com/products/64899/Intel-Core-i7-3610QM-Processor-6M-Cache-up-to-3_30-GHz

notebook mobile boxes were not generally designed for server roles, unlike desktops

newer processors will gain better support with Windows 8.1 professional which now included Hyper-V as a feature.

you will need to consult cpu manuals deeply to identify suitable models

I use 8.1 as opposed to 8 primarily to encourage world+dog to install all updates.

I have been doing lots of updates this year for clients with older XP rigs, with some more recent ones too.

Most of them according to the taskman lack the virtualization capacility

sorry, posted the wrong graphic

this is the cpu panel to check

I use 8.1 as opposed to 8 primarily to encourage world+dog to install all updates.

I have been doing lots of updates this year for clients with older XP rigs, with some more recent ones too.

Most of them according to the taskman lack the virtualization capacility

Older AM2 processors can run Hyper-V, I have an old AthlonX2 CPU that does support Hyper-V with Server 2008 R2. 

I had XP running that M2NBP-VM CSM until a cruddy NVIDIA driver trashed it.

I have not tried newer SKUs of Windows server on that rig

I replaced that rig with the M4A77D which allowed me to use DDR2 and the more recent Phenom II CPU I use now. The Phenom runs everything well.

The Hyper-V that comes with Windows 8.1 is a new HAL with no more IDE virtual hardware. So the CPU architecture requirements chanced.

Manuals call for a feature called SLAT, for second level address translation.

So getting back to my question, should I be contacting MS or Dell?  Actually, I am all for more troubleshooting steps if you have them.

I suggest contacting Dell as it is their rig

Hello,

I am encountering the same issue here, Win 8.1 (fully updated), running Hyper V, VMs used to work, but not anymore. I want to avoid the hassle of reinstalling the whole PC (as that will take some time and I will wait for Win 10 :). I have double and triple checked the Virtualization et al. settings and when installing for example a Win 2012 R2 Trial server on a separate partition HyperV VMs work just fine.

Yes, I have uninstalled and reinstalled the Hyper V, including by command line. Twice. If it's a video driver, it'll have to wait.

I am getting the following error when I try to start a brand new VM: "the application encountered an error while attempting to change the state of {VM ID} could not initialize". 

I have enabled the debug logging in event viewer for HyperV and I get the following errors when I try to start the VM:

Hyper-V-VMMS / Analytic:

Event IDs are in front of the lines: 

1102: VmException caught in VmmsRealizedVirtualMachine::StartInternal (HRESULT = 0x800700C1)

1202: throw VmGeneralSystemException((DWORD) 193)
1102: Failed to initialize worker process for VM 7CB0649B-74DB-40C7-A129-22EE62323A0B - HRESULT = 0x800700C1

I get the following errors when I start the PC; W means those are warnings:

1101/Warning:TesthooksWrapper::Initialize: Load RdvTestHooks.dll failed. HRESULT=0x8007007e. All test hooks checks will return default values.

1102:Synth3dPhysicalGPUManager::BecomeFunctional faced errors 0

1101/W: Failed to set remoting certificate for VM 7CB0649B-74DB-40C7-A129-22EE62323A0B!

1101/W: Failed to set allowed hash algorithms for VM 7CB0649B-74DB-40C7-A129-22EE62323A0B!

1801/W: Failed to set allowed hash algorithms for VM 7CB0649B-74DB-40C7-A129-22EE62323A0B!

1801/W: Failed to register decoupled WMI provider VmmsWmiEventProvider in namespace root\virtualization! HRESULT = 0x80041011

1101/W: VmmsVirtualMachine::GetBackupSnapshot: ReadString failed for 7CB0649B-74DB-40C7-A129-22EE62323A0B! HRESULT = 0x80070002

1101/W: Synth3dPhysicalGPUManager::InitResourcePoolCachedData: m_InitializationCompleteEvt is NULL. Skipping rest of initialization.

1101/W: VmmsVirtualMachine::GetBackupSnapshot: ReadString failed for 7CB0649B-74DB-40C7-A129-22EE62323A0B! HRESULT = 0x80070002

1202: throw VmGeneralSystemException((DWORD) 50)

1801/W: Attempt to complete a WMI operation that has already been completed - ignored!

In the Hyper-V-Worker Log - Admin, when I try to run the VM: 

3040: 'test1' could not initialize. (Virtual machine ID 7CB0649B-74DB-40C7-A129-22EE62323A0B)

In the Analytic section there are 2 errors, event id 1520, each time I try to start the VM: 

[Virtual machine 7CB0649B-74DB-40C7-A129-22EE62323A0B] vm\dv\vmb\vdevmanifest.cpp(749) in VirtualDeviceManifest::CreateVirtualDeviceInstance : CoCreateInstance failed 800700c1 for the VDev (Microsoft Hyper-V Activation Component) GUID {BC12C717-8898-4688-8EE4-2CD14894F8EA}.

[Virtual machine 7CB0649B-74DB-40C7-A129-22EE62323A0B] Failed to initialize Virtual Motherboard (HRESULT 0x800700c1).

In the VDEV-Analytic section these errors keep on going, event id 10560, I have included only some, there are many more:

[Virtual machine 7CB0649B-74DB-40C7-A129-22EE62323A0B] CreateVirtualDevice {f3cf6965-e8d3-44a9-9b7d-a0a04245ea75}
[Virtual machine 7CB0649B-74DB-40C7-A129-22EE62323A0B] AddServiceProvider {5a753463-f272-4d06-a553-fbfb47c13628}
[Virtual machine 7CB0649B-74DB-40C7-A129-22EE62323A0B] CreateVirtualDevice {197f74e3-b84b-46de-8ae6-8282f1cd181c}
[Virtual machine 7CB0649B-74DB-40C7-A129-22EE62323A0B] AddServiceProvider {5a753463-f272-4d06-a553-fbfb47c13628}
[Virtual machine 7CB0649B-74DB-40C7-A129-22EE62323A0B] CreateVirtualDevice {58f75a6d-d949-4320-99e1-a2a2a2576d58}
[Virtual machine 7CB0649B-74DB-40C7-A129-22EE62323A0B] AddServiceProvider {d24555f2-66ad-4a3b-bcd8-7777ac1508ca}

etc. etc...

In Hyper-V-Config Section/Analytic, Event ID 514, all errors, at boot time:

[VMID  - ] throw VmGeneralSystemException((DWORD) 183)

I'm happy to work with you for further debugging, maybe it turns out it can be of real help to someone.

In the meantime, I will enjoy the HyperV only from the server installation :(

Cheers,

Mihai